feat: use uv lock file - #1427

Thanks for the changes @SMoraisAnsys, I left a couple of comments.

There is one other thing I have been thinking about, why can't we just use the uv lock files automatically once detected rather than exposing an explicit input for it (similar to how there is no input for poetry). IMO, a project that already uses a lock file would expect its dependencies to be install from it.

I'm fine with detecting it and activating it by default. My only concern is the sudden change of behavior for people that still work with version tag and/or don't read every release note carefully.

Thanks for the changes @SMoraisAnsys, I left a couple of comments.
There is one other thing I have been thinking about, why can't we just use the uv lock files automatically once detected rather than exposing an explicit input for it (similar to how there is no input for poetry). IMO, a project that already uses a lock file would expect its dependencies to be install from it.

I'm fine with detecting it and activating it by default. My only concern is the sudden change of behavior for people that still work with version tag and/or don't read every release note carefully.

I could wait for this to get merged before v11 release, that way we have a graceful way of introducing this change. We can clearly document behavior change in the migration guide and those using tags won't be affected until they explicitly bump. What do you think?

I think out of all the actions this has been extended to, _doc-build-windows, check-vulnerabilities and tests-pytest are the only ones not being tested directly in the actions pipelines. It will be nice if we can test those prior to merging, just to be certain things run fine.

Thanks for the major changes @SMoraisAnsys!

I was working on adding those tests in the other PR. If the changes aren't pushed, I'll update that (miss on my side) (it was pushed).

Converted to draft until testing is fully performed (still some misses)